System and method for data transmission for appliance

ABSTRACT

A system and method for data transmission and performance improvement for an appliance is provided. The system includes an appliance including a controller operably connected to a network computing device. The controller is configured to transmit a packet to a network computing device. The packet includes genealogical data for the appliance encoded in a positional numeral system. The network computing device is configured to receive the packet and decode the genealogical data for the appliance. Decoding includes translating the positional numeral system to an appliance configuration.

FIELD OF THE INVENTION

The present subject matter relates generally to consumer or commercialappliances, such as domestic appliances, and more particularly tosystems and methods for diagnostics and transmitting data to and fromsuch appliances.

BACKGROUND OF THE INVENTION

Conventional residential or commercial appliances may include componentsthat may have defects from the supplier. In certain instances,components from certain lot numbers or batches may include defectivesub-components. After the appliance has been manufactured, such defectsmay typically be remedied through manufacturer recalls or warrantyclaims.

Conventional residential or commercial appliances may include componentsthat are utilized with other types of components, or may be operateddifferently based on the appliance or appliance model to which thecomponent is installed. Differences or issues in performance orreliability may become apparently only after the appliance has beenoperated by an end-user. Remedies to undesired performance orreliability may be available for the appliance. However, an issue forappliance manufacturers is finding the appliances that have thedefective or under-performing components.

Conventional residential or commercial appliances collect and store dataduring operation that can later be used for diagnostic or otherpurposes. This data is normally collected on a cycle-by-cycle basis andincludes various system parameters depending on the type of appliance.For example, a dishwasher may collect data related to water temperature,water level, sensors states, fault conditions, etc. This data may beuseful for a number of purposes, e.g., including service diagnostics,consumer use analysis, etc.

However, datasets or files associated with collection of such data aregenerally large. Such large files may be prohibitive for streamingthrough a network for data analysis. Additionally, an aggregation ofsuch large files at a server may result in such large amounts ofinformation being generated and stored that a manufacturer or other usermay be technically or financially prohibited from receiving or retainingthe data for useful purposes.

Still further, conventional residential or commercial appliances mayinclude components that are sourced from multiple different suppliers,such as to reduce risks by the manufacturer associated with sole-sourcesuppliers. While such component multi-sourcing may reduce supply chainrisks, such practices may introduce differences in quality orperformance such as described above. In some instances, data may beavailable relating to one of these issues. However, such as providedabove, such data may be inaccessible for manufacturers to utilize toaddress such problems as provided above.

Accordingly, systems and methods for data transmission, diagnostics, andperformance improvement are desired.

BRIEF DESCRIPTION OF THE INVENTION

Aspects and advantages of the invention will be set forth in part in thefollowing description, or may be obvious from the description, or may belearned through practice of the invention.

An aspect of the present disclosure is directed to a system for datatransmission for an appliance. The system includes an applianceincluding a controller operably connected to a network computing device.The controller is configured to transmit a packet to a network computingdevice. The packet includes genealogical data for the appliance encodedin a positional numeral system. The network computing device isconfigured to receive the packet and decode the genealogical data forthe appliance. Decoding includes translating the positional numeralsystem to an appliance configuration.

Another aspect of the present disclosure is directed to acomputer-implemented method for data transmission and diagnostics for anappliance. The method includes transmitting a packet to a remote serverthrough a network, wherein the packet includes genealogical data encodedin a positional numeral system; receiving the packet at the remoteserver; and decoding, at the remote server, the genealogical data forthe appliance, wherein decoding includes translating the positionalnumeral system to an appliance configuration.

These and other features, aspects and advantages of the presentinvention will become better understood with reference to the followingdescription and appended claims. The accompanying drawings, which areincorporated in and constitute a part of this specification, illustrateembodiments of the invention and, together with the description, serveto explain the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

A full and enabling disclosure of the present invention, including thebest mode thereof, directed to one of ordinary skill in the art, is setforth in the specification, which makes reference to the appendedfigures.

FIG. 1 provides a schematic diagram depicting the system executing stepsof the method for data transmission and performance improvement for anappliance in accordance with aspects of the present disclosure.

FIG. 2 provides a flowchart outlining steps of a method for datatransmission and performance improvement for an appliance in accordancewith aspects of the present disclosure.

Repeat use of reference characters in the present specification anddrawings is intended to represent the same or analogous features orelements of the present invention.

DETAILED DESCRIPTION

Reference now will be made in detail to embodiments of the invention,one or more examples of which are illustrated in the drawings. Eachexample is provided by way of explanation of the invention, notlimitation of the invention. In fact, it will be apparent to thoseskilled in the art that various modifications and variations can be madein the present invention without departing from the scope of theinvention. For instance, features illustrated or described as part ofone embodiment can be used with another embodiment to yield a stillfurther embodiment. Thus, it is intended that the present inventioncovers such modifications and variations as come within the scope of theappended claims and their equivalents.

As used herein, the terms “first,” “second,” and “third” may be usedinterchangeably to distinguish one component from another and are notintended to signify location or importance of the individual components.The terms “includes” and “including” are intended to be inclusive in amanner similar to the term “comprising.” Similarly, the term “or” isgenerally intended to be inclusive (i.e., “A or B” is intended to mean“A or B or both”). In addition, here and throughout the specificationand claims, range limitations may be combined and/or interchanged. Suchranges are identified and include all the sub-ranges contained thereinunless context or language indicates otherwise. For example, all rangesdisclosed herein are inclusive of the endpoints, and the endpoints areindependently combinable with each other. The singular forms “a,” “an,”and “the” include plural references unless the context clearly dictatesotherwise.

Approximating language, as used herein throughout the specification andclaims, may be applied to modify any quantitative representation thatcould permissibly vary without resulting in a change in the basicfunction to which it is related. Accordingly, a value modified by a termor terms, such as “generally,” “about,” “approximately,” and“substantially,” are not to be limited to the precise value specified.In at least some instances, the approximating language may correspond tothe precision of an instrument for measuring the value, or the precisionof the methods or machines for constructing or manufacturing thecomponents and/or systems. For example, the approximating language mayrefer to being within a 10 percent margin, i.e., including values withinten percent greater or less than the stated value. In this regard, forexample, when used in the context of an angle or direction, such termsinclude within ten degrees greater or less than the stated angle ordirection, e.g., “generally vertical” includes forming an angle of up toten degrees in any direction, e.g., clockwise or counterclockwise, withthe vertical direction V.

Referring now to FIG. 1 , a system of appliances 100 will be describedaccording to exemplary embodiments of the present subject matter. Ingeneral, system of appliances 100 may include any suitable number, type,and configuration of appliances, remote servers, network devices, and/orother external devices. Some of these appliances 100 may be able tocommunicate with each other or are otherwise interconnected. Thisinterconnection, interlinking, and interoperability of multipleappliances and/or devices may commonly be referred to as “smart home” or“connected home” appliance interconnectivity.

FIG. 1 illustrates system of appliances 100 according to exemplaryembodiments of the present subject matter. As shown, system ofappliances 100 generally includes a first appliance 102, or furthermorea second appliance, or furthermore and a third appliance, etc. Detailsregarding the operation of first appliance 102, second appliance, andthird appliance may be understood by one having ordinary skill in theart and detailed discussion is omitted herein for brevity. However, itshould be appreciated that the specific appliance types andconfigurations are only exemplary and are provided to facilitatediscussion regarding the use and operation of an exemplary system ofappliances 100. The scope of the present subject matter is not limitedto the number, type, and configurations of appliances set forth herein.

For example, the system of appliances 100 may include any suitablenumber and type of “appliances,” such as “household appliances.” Theseterms are used herein to describe appliances typically used or intendedfor common domestic tasks, e.g., such as the appliances as illustratedin the figures. According to still other embodiments, these “appliances”may include but are not limited to a refrigerator, a dishwasher, amicrowave oven, a cooktop, an oven, a washing machine, a dryer, a waterheater, a water filter or purifier, an air conditioner, a space heater,and any other household appliance which performs similar functions.Moreover, although only three appliances are illustrated, variousembodiments of the present subject matter may also include anothernumber of appliances, each of which may generate and store data.

In addition, it should be appreciated that system of appliances 100 mayinclude one or more external devices, e.g., devices that are separatefrom or external to the one or more appliances, and which may beconfigured for facilitating communications with various appliances orother devices. For example, the system of appliances 100 may include orbe communicatively coupled with a remote user interface device 110 thatmay be configured to allow user interaction with some or all appliancesor other devices in the system of appliances 100.

In general, remote user interface device 110 may be any suitable deviceseparate and apart from appliances that is configured to provide and/orreceive communications, information, data, or commands from a user. Inthis regard, remote user interface device 110 may be an additional userinterface to the user interface panels of the various appliances withinthe system of appliances 100. In this regard, for example, the userinterface device 110 may be a personal phone, a smartphone, a tablet, alaptop or personal computer, a wearable device, a smart home system, oranother mobile or remote device. For example, the separate device may bea smartphone operable to store and run applications, also known as“apps,” and the remote user interface device 110 be provided as asmartphone app.

As will be described in more detail below, some or all of the system ofappliances 100 may include or be communicatively coupled with a remoteserver 112 that may be in operative communication with some or allappliances within system of appliances 100. Thus, user interface device110 and/or remote server 112 may refer to one or more devices that arenot considered household appliances as used herein. In addition, devicessuch as a personal computer, router, network devices, and other similardevices whose primary functions are network communication and/or dataprocessing are not considered household appliances as used herein.

As illustrated, each of appliance 102, remote user interface device 110,or any other devices or appliances in system of appliances 100 mayinclude or be operably coupled to a controller, identified hereingenerally by reference numeral 120. As used herein, the terms“processing device,” “computing device,” “controller,” or the like maygenerally refer to any suitable processing device, such as a general orspecial purpose microprocessor, a microcontroller, an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field-programmable gate array (FPGA), a logicdevice, one or more central processing units (CPUs), a graphicsprocessing units (GPUs), processing units performing other specializedcalculations, semiconductor devices, etc. In addition, these“controllers” are not necessarily restricted to a single element but mayinclude any suitable number, type, and configuration of processingdevices integrated in any suitable manner to facilitate applianceoperation. Alternatively, controller 120 may be constructed withoutusing a microprocessor, e.g., using a combination of discrete analogand/or digital logic circuitry (such as switches, amplifiers,integrators, comparators, flip-flops, AND/OR gates, and the like) toperform control functionality instead of relying upon software.

Controller 120 may include, or be associated with, one or more memoryelements or non-transitory computer-readable storage mediums, such asRAM, ROM, EEPROM, EPROM, flash memory devices, magnetic disks, or othersuitable memory devices (including combinations thereof). These memorydevices may be a separate component from the processor or may beincluded onboard within the processor. In addition, these memory devicescan store information and/or data accessible by the one or moreprocessors, including instructions that can be executed by the one ormore processors. It should be appreciated that the instructions can besoftware written in any suitable programming language or can beimplemented in hardware. Additionally, or alternatively, theinstructions can be executed logically and/or virtually using separatethreads on one or more processors.

For example, controller 120 may be operable to execute programminginstructions or micro-control code associated with an operating cycle ofan appliance. In this regard, the instructions may be software or anyset of instructions that when executed by the processing device, causethe processing device to perform operations, such as running one or moresoftware applications, displaying a user interface, receiving userinput, processing user input, etc. Moreover, it should be noted thatcontroller 120 as disclosed herein is additionally, or alternatively,configured to store, execute, or otherwise operate or perform any one ormore methods, method steps, or portions of methods as disclosed herein.For example, in some embodiments, methods disclosed herein may beembodied in programming instructions stored in the memory and executedby controller 120. The memory devices may also store data that can beretrieved, manipulated, created, or stored by the one or more processorsor portions of controller 120. One or more database(s) can be connectedto controller 120 through any suitable communication module,communication lines, or network(s).

Referring still to FIG. 1 , a schematic diagram of an externalcommunication system 130 will be described according to an exemplaryembodiment of the present subject matter. In general, externalcommunication system 130 is configured for permitting interaction, datatransfer, and other communications between and among one or more of theappliances, remote user interface device 110, and the remote server 112.For example, this communication may be used to transmit packets of datathrough a network 132 and to the remote server 112 and to receive at oneor more appliances an operational parameter adjustment corresponding toone or more of operating parameters, cycle settings, user instructionsor notifications, performance characteristics, user preferences, or anyother suitable information for improved performance of one or moreappliances within system of appliances 100.

In addition, remote server 112 may be in communication with an applianceand/or remote user interface device 110 through the network 132. In thisregard, for example, remote server 112 may be a cloud-based server 112,and is thus located at a distant location, such as in a separate state,country, etc. According to an exemplary embodiment, remote userinterface device 110 may communicate with a remote server 112 overnetwork 132, such as the Internet, to transmit/receive data packets orinformation, provide user inputs, receive user notifications orinstructions, interact with or control the appliance, etc. In addition,remote user interface device 110 and remote server 112 may communicatewith the appliance to communicate similar information.

In general, communication between an appliance, remote user interfacedevice 110, remote server 112, and/or other user devices or appliancesmay be carried using any type of wired or wireless connection and usingany suitable type of communication network, non-limiting examples ofwhich are provided below. For example, remote user interface device 110may be in direct or indirect communication with the appliance throughany suitable wired or wireless communication connections or interfaces,such as network 132. For example, network 132 may include one or more ofa local area network (LAN), a wide area network (WAN), a personal areanetwork (PAN), the Internet, a cellular network, any other suitableshort- or long-range wireless networks, etc. In addition, communicationsmay be transmitted using any suitable communications devices orprotocols, such as via Wi-Fi®, Bluetooth®, Zigbee®, wireless radio,laser, infrared, Ethernet type devices and interfaces, etc. In addition,such communication may use a variety of communication protocols (e.g.,TCP/IP, HTTP, SMTP, FTP), encodings or formats (e.g., HTML, XML), and/orprotection schemes (e.g., VPN, secure HTTP, SSL).

External communication system 130 is described herein according to anexemplary embodiment of the present subject matter. However, it shouldbe appreciated that the exemplary functions and configurations ofexternal communication system 130 provided herein are used only asexamples to facilitate description of aspects of the present subjectmatter. System configurations may vary, other communication devices maybe used to communicate directly or indirectly with one or moreassociated appliances, other communication protocols and steps may beimplemented, etc. These variations and modifications are contemplated aswithin the scope of the present subject matter.

Now that the construction of system of appliances 100 and externalcommunication system 130 have been presented according to exemplaryembodiments, an exemplary method 1000 for data transmission for anappliance will be described. Although the discussion below refers to theexemplary method 1000 of operating an appliance from system ofappliances 100, one skilled in the art will appreciate that theexemplary method 1000 is applicable to the memory usage and/or dataallocation of any suitable number, type, and configuration ofappliances. In exemplary embodiments, the various method steps asdisclosed herein may be performed by one or more controllers (e.g., suchas controllers 120) or by a separate, dedicated controller that may belocated locally on one or more of the appliances, remotely on a remoteserver, or remote user interface device 110, etc.

Notably, as explained briefly described above, consumer and commercialappliances commonly generate large amounts of data during normaloperation. This data, referred to herein generally as “diagnostics data”or “appliance performance data”, may be used for a variety of purposesby the user of the appliance or a third-party (e.g., such as themanufacturer). For example, this data may be used for performanceanalysis, diagnostic analysis, fault detection, root cause analysis,analysis of consumer use habits, or for any other suitable purposegenerally intended for improving appliance performance and usersatisfaction.

Notably, the receipt and storage of such large volumes of data may beexpensive and the onboard storage capacity of conventional appliancesmay become a limiting factor in data storage, particularly as appliancesbecome more complex and the need for more data increases. In thisregard, as described briefly above, each appliance controller (e.g.,controllers 120) may have a limited amount of system memory that iscapable of storing diagnostics data.

Furthermore, data packets as described herein include, at least, aconfiguration identifier that identifies one or more component types atthe appliance, a manufacturer identifier that identifies a supplier ormanufacturer of each component, a logistical identifier that identifiesa lot number, a batch number, a serial number, or other manufacturingdata of the component, a version identifier corresponding to software orcontrol algorithm associated with the component, or other identifyinginformation of specific components of the appliance, which may bereferred to herein as “genealogical data”. In particular, suchgenealogical data allows for differentiation between appliances of thesame model type (e.g., an appliance of model A) based on one or more ofthe configuration identifier, manufacturer identifier, logisticalidentifier, version identifier, or combinations thereof, such as todistinguish among appliances of the same model type (e.g., plurality ofappliances of model A) having components from various suppliers, lotnumbers, batch numbers, version numbers, etc.

The type of appliance data that is desirable is largely dependent on theend user of such data. For example, a service technician who istroubleshooting an appliance fault may desire a large number of cyclerecords or a long history of appliance operation but may requirerelatively few recorded parameters in order to determine the root causeof such faults during a maintenance visit or service call. By contrast,a data analyst focusing on user routines or habits from a remotelocation may not require as many cycle records to be saved by themachine since the data is streamed and stored in a remote server. Otherusers may desire an entirely different combination of data for theirpurposes. The situations result in a conflict between desirablediagnostics data that is stored and the available system resources.Accordingly, aspects of the present subject matter are directed tomethods for improved storage of diagnostics data in an appliance.

Referring now to FIG. 2 , embodiments of a method for data transmissionfor an appliance is provided (hereinafter, “method 1000”). Embodimentsof the method 1000, or steps thereof, may be executed at one or moreappliances, such as any one or more of appliances or the system ofappliances 100, such as described in regard to FIG. 1 . However, itshould be appreciated that method 1000 may be stored or executed withother embodiments of appliances or networks. Appliances may include, butare not limited to, a refrigerator appliance, a freezer appliance, alaundry washing appliance, a laundry drying appliance, a dishwashingappliance, a cooking appliance, a microwave appliance, an airconditioner appliance, a heater appliance, a beverage-maker appliance,or other appropriate type of appliance that may be connected to anetwork and server. Steps of the method 1000 may be stored asinstructions and executed as operations at controller 120, remote server112, or user interface device 110 and transmitted via network 132.However, it should be appreciated that method 1000 may be stored,executed, and operates in other embodiments of a network, computingdevice, server, or appliance without substantially deviating from thepresent subject matter.

Embodiments of the system 100 or method 1000 herein provide an appliancegenealogy system including a cloud heartbeat of an encoded networkpacket transmitted at a desired frequency or rate from one or moreconnected appliances to a network, such as a cloud network (e.g.,network 132). The packet is decoded at a remote server (e.g., remoteserver 112), such as to determine genealogical data for the appliance. Aplurality of packets received from each appliance may be compared to oneanother, or particularly to performance data associated with theappliances. An operational parameter adjustment may be determined basedon comparing the packets. The operational parameter adjustment mayinclude a control change, software change, speed, frequency, amplitude,angular, rate, velocity, acceleration, volume, or other quantitativechange or change to an operating limit of an associated component, or adetermination of physical hardware change, such as to be implemented bya technician. In one instance, the physical hardware change may be arecall, replacement, or performance improvement of a component based ona particular manufacturer, supplier, lot number, or other logisticalidentifier associated with particular component(s) at the appliance.Accordingly, embodiments of the system and method herein may allow fortargeted recalls, replacements, or improvements in contrast to recallsof entire model families of appliance.

Referring to FIG. 2 , embodiments of the method 1000 include at 1002encoding genealogical data to the packet. As described above and furtherherein, the genealogical data includes one or more of a configurationidentifier, a manufacturer identifier, a logistical identifier, aversion identifier, or combinations thereof Embodiments of the method1000 include at 1010 transmitting a packet to a network computingdevice, such as to remote server through a network. The packet includesappliance data for the appliance encoded in a positional numeral system.

In particular embodiments, the encoded packet includes a quantity ofbytes having a positional numeral system greater than base 2. Inparticular embodiments, the positional numeral system is hexadecimal orbase 12 (e.g., 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F). The method1000 includes at 1020 receiving the packet at the remote server and at1030 decoding, at the remote server, the genealogical data for theappliance. At the remote server, a computing device decodes or comparesthe positional numeral system of the packet to a decoder, such as atable, schedule, chart, list, or other decoder dataset identifyinggenealogical data from the packet. The method 1000 at 1030 mayparticularly include translating the positional numeral system to anappliance configuration. The appliance configuration includes aparticular combination of component types (e.g., a particularcombination of component types, logistical data, The packet, the decoderdataset, or both, is stored at the remote server or transmitted toanother appropriate database, server, or computing device. The packetcontains genealogical data such as described above and further herein.

In particular embodiments, the packet contains bytes corresponding to anappliance configuration for the appliance from which the packet istransmitted. For instance, a first byte, or a plurality of first bytes,may each correspond to a component type for the appliance. The componenttype may include, but is not limited to, a motor, a compressor, anevaporator, a condenser, a heat exchanger, a fan, a control unit, acomputing device, etc. of the appliance. The component type mayparticularly include any appropriate component or key component that maybe serviced or serviceable by a technician, actuatable hardware, controlcomponents, control boards, etc.

In another instance, a second byte, or a plurality of second bytes, maycorrespond to a supplier or manufacturer identifier corresponding firstbyte or plurality of first bytes for the component type. For example,the component type corresponding to the first byte may be manufacturedor sourced from various suppliers or manufacturers. The second byte orplurality of second bytes corresponds to the specific supplier ormanufacturer of the component corresponding to the first byte orplurality of first bytes.

In still another instance, a third byte, or a plurality of third bytes,may correspond to a lot number, a serial number, or other logisticalidentifier for the component type. For example, the supplier ormanufacturer corresponding to the second byte or plurality of secondbytes corresponds the logistical identifier of the component type fromthe supplier or manufacturer. It should be appreciated that, in certainembodiments, the manufacturer identifier and the logistical identifiermay be contained in the same bytes, such that the logistical identifierfurthermore identifies the supplier or manufacturer.

Accordingly, the relatively small packet contains genealogical datacorresponding to the specific combination of components, componentsuppliers, and logistical data for each appliance. In particular, thepacket encoding the genealogical data in a positional numeral systemformat allows for large combinations or potential combinations ofconfigurations to be stored and transmitted in relatively small datafile sizes. In a still particular embodiment, the packet encoding thegenealogical data in a hexadecimal positional numeral system allows forlarge combinations of appliance configurations to be stored andtransmitted in relatively small data file sizes.

In another embodiment, the packet may include a fourth byte, or aplurality of fourth bytes, corresponding to an appliance type. It shouldbe appreciated that particular configurations of appliance, such as maybe encoded in one or more bytes as described above, may correspond tospecific appliance types. Accordingly, appliance type data may beincluded as the fourth byte in the packet, or may be inferred from thecombination of components included in the packet. For instance, thecombination of components may include components that correspond tospecifically a refrigerator appliance, a freezer appliance, a laundrywashing appliance, a laundry drying appliance, a dishwashing appliance,a cooking appliance, a microwave appliance, an air conditionerappliance, a heater appliance, a beverage-maker appliance, or otherappropriate type of appliance that may be connected to connected to thenetwork 132.

As provided at 1020, the remote server receives the packet and at 1030decodes the positional numeral values to translate the packet into along-form description of a configuration of the appliance, referred toherein as “appliance configuration.” The appliance configurationincludes details relating to one or more of the component types, thesupplier or manufacturer of each component type, a lot number, batchnumber, assembly or manufacturing data, or other manufacturing datacorresponding to the component, or other information as may be includedin the packet, relating to the specific appliance.

Various embodiments of methods and system provided herein furtherinclude periodically transmitting the packet, such as a “cloudheartbeat”. A corresponding frequency or rate may be one per hour, orone per day, or one per week, or one per month, etc. In certainembodiments, method 1000 includes at 1022 generating a timestampcorresponding to each packet received. In particular embodiments,generating the timestamp is performed at the remote server or thenetwork, such as to allow for a reduced size of the packet generated,stored, or transmitted through the network. Accordingly, when values ofthe packet change, a timestamp is generated at the remote server tocorrelate the change in appliance configuration to a time at which theconfiguration occurred. Particularly, such temporal data may begenerated and received without necessitating generation and transmissionby the appliance, such as allowing for relatively smaller packet sizes.Stated differently, the packet may not require values corresponding toparticular timestamps. Rather, embodiments of the system and methodcompare changes in the positional numeral values to timestampscorresponding to when the packet is received at the remote server suchas to determine a time at which component changes or control changeshave occurred.

Still various embodiments of the method 1000 include at 1024 generatinga location tag corresponding to each packet. In a particular embodiment,the remote server may generate a location tag corresponding to eachpacket, such as to correlate a location or custody of the appliance tothe packet. Particularly, such location data may be generated andreceived without necessitating generation and transmission by theappliance, such as allowing for relatively smaller packet sizes. Stateddifferently, the packet may not require values corresponding toparticular location of the appliance. Rather, embodiments of the systemand method compare changes in the positional numerical values to changesin location tags corresponding to determine whether a physical locationof the appliance has moved. More particularly, the method and system maydetermine when an appliance has moved to a different building.

As described herein, certain embodiments of the method 1000 include at1034 determining an operational parameter adjustment. In a particularembodiment, method 1000 includes at 1032 comparing the applianceconfiguration to performance data. Method 1000 at 1034 may determine theoperational parameter adjustment based on comparing the applianceconfiguration to performance data. In one embodiment, comparing theappliance configuration to performance data includes comparing theappliance configuration corresponding to a plurality of packets receivedfrom a plurality of appliances to a plurality of performance datacorresponding to the respective plurality of appliances.

As provided in FIG. 1 , a technician, a manufacturer, or both, maygenerate an encoded packet, such as described in regard to step 1002.When a component is replaced at an appliance, a technician or other usermay update the packet information to reflect changed component,corresponding manufacturer identifier, logistical identifier, versionidentifier, or other data associated with the changed component. Thepacket transmitted to the remote server (e.g., method 1000 at 1010) thencontains genealogical data corresponding to the updated applianceconfiguration. In certain embodiments, temporal data or location dataassociated with the packet (e.g., method 1000 at 1022 or 1024) isattached or correlated to the packets, such as to identify when or wherethe appliance configuration change occurred.

System 100 and method 1000 may further compare the packets received fromeach of a plurality of appliances (e.g., method 1000 at 1032) andidentify trends, correlations regressions, interpolations, orextrapolations associated with the various appliance configurations, ormore particularly, genealogical data such as configuration identifiers,manufacturer identifiers, logistical identifiers, or versionidentifiers. For instance, comparing the packets may identify that acertain lot number of a particular component is replaced at a certainrate, or after a certain period of time, in contrast to other lotnumbers of the component. In one instance, determining an operationalparameter adjustment, such as a quality analysis, may determine that thelot number of the component is defective and a recall or replacement maybe ordered relative to the specific lot number for the component, ratherthan for the appliance model generally or the component generally. Inanother instance, the quality analysis may determine that the lot numberof the component is defective and a software change may be orderedrelative to the specific lot number of the component. In still anotherinstance, the quality analysis may determine that the lot number of thecomponent is defective and a software change may be ordered relative tothe specific lot number of the component when operating with one or moreother specific components, or lot numbers thereof.

It should be appreciated that embodiments of the method 1000 and system100 allow for other instances for determining performance, failure, ordiagnostics based on supplier or manufacturer identifiers, softwareversion identifiers, or combinations thereof. For instance, the qualityanalysis may determine that certain combinations of components, orparticular suppliers, lot numbers, or versions thereof, may performbetter or worse than when combined with other configurations. As such, acomponent may be replaced, or avoided in combination with othercomponents, or a particular software version may be implemented orchanged, based on the specific combination with other components.Accordingly, the component may be utilized with better performance inother appliance configurations rather than being scrapped or otherwisetreated as defective.

Accordingly, embodiments of the method 1000 and system 100 providedherein allow for determining performance or failure of various applianceconfigurations. More particularly, embodiments provided herein allow fordetermining performance or failure without necessitating diagnostics orperformance data to be transmitted in the packet from the appliancethrough the network. As such, embodiments provided herein allow forimproved maintenance, performance analysis, or failure determinationusing less data and smaller file sizes.

Embodiments of the method 1000 may further include at 1040 transmittingan operational parameter adjustment to the appliance via the remoteserver and the network based at least on the decoded genealogical data.As provided herein, the operational parameter adjustment may include asoftware change, a component change, or a signal indicative of ahardware, software, or other operational change to be performed at theappliance.

In certain embodiments of the method 1000, the packet may include afifth byte or plurality of fifth bytes defining an operating conditionof the component. For instance, the positional numeral value defining ahexadecimal may correlate to one of up to sixteen operating conditions(or more if a plurality of fifth bytes is utilized). In a particularembodiment, a value of 1 may correspond to a “new” or “best” operatingcondition, and a value of F (or G in certain nomenclature) maycorrespond to a “worst” operating condition, and values therebetween(e.g., values 2 through E or F) may correspond to gradations ofoperating conditions between 1 and F. As such, the packet may includedetailed performance data corresponding to each component type, supplieror manufacturer identifier, logistical identifier, version identifier,or other genealogical datum, or combinations of appliance configuration.

Embodiments of the system 100 and method 1000 may include generating, atthe network or the remote server, a first dataset corresponding to achronological history, a geographic history, or both, of the packet,referred to as “heartbeat history” in FIG. 1 . The method 1000 performsgenealogical data decoding, such as at the network or remote server. Themethod 1000 may further transmit or store such long-form data at agenealogy database. The genealogy database may include performance dataof the plurality of packets received from the plurality of appliances.Users may obtain or access the genealogy database to determine anoperational parameter adjustment, such as described herein. Theoperational parameter adjustment may then be transmitted to theappliance as a software change or a signal indicative of a hardwarechange.

Embodiments of the system and method provided herein allow forrelatively small packets to transmit data corresponding to specificcombinations of component type and lot or serial number for eachappliance. When received by an appliance manufacturer, a user or qualityanalysis may compare performance of specific component types, orspecific lots, batches, or serial numbers of the component, or softwareor controller versions, such as to determine whether certain applianceconfigurations, or more particularly, e.g., suppliers, manufacturers,lot numbers, manufactured batches, controller versions, geographiclocations, temporal periods, or combinations with particular components,or specific configurations thereof, may correspond to improved ordeleterious performance, certain success or failure rates, or otherperformance indicators. Still further, such determinations may beperformed utilizing relatively small data packets received over a periodof time that correspond to specific appliance configurations and changestherein.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they include structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal languages of the claims.

1. An appliance data transmission system, the system comprising: anappliance comprising a controller operably connected to a networkcomputing device, the controller configured to encode genealogical datato a packet in hexadecimal format, wherein the genealogical data isencoded in a positional numeral system, the genealogical data comprisinga configuration identifier, a manufacturer identifier, a logisticalidentifier, a version identifier, or combinations thereof, allowing fordifferentiation of appliances of the same model type based on one ormore of the configuration identifier, the manufacturer identifier, thelogistical identifier, or the version identifier, the controllerconfigured to periodically transmit the packet to the network computingdevice, wherein the network computing device is configured to receivethe packet and decode the genealogical data for the appliance, whereindecoding comprises translating the positional numeral system to anappliance configuration, and wherein the network computing device isconfigured to compare genealogical data from a plurality of packetsperiodically received from each of a plurality of the appliances, andwherein the network computing device is configured to comparegenealogical data from the periodically transmitted packets to determineat the remote server an operational parameter adjustment correspondingto one or more of the configuration identifier, the manufactureridentifier, the logistical identifier, or the version identifierassociated with one or more appliance configurations corresponding toone or more appliances of the plurality of appliances.
 2. The system ofclaim 1, wherein the network computing device is configured to transmitthe operational parameter adjustment, wherein the operational parameteradjustment comprises a control change, a software change, an operatinglimit, or an identification of component replacement at the appliance tobe implemented by a technician.
 3. (canceled)
 4. The system of claim 1,wherein the network computing device is configured to determine theoperational parameter adjustment based on comparing the applianceconfiguration to performance data.
 5. (canceled)
 6. The system of claim4, wherein determining the operational parameter adjustment comprisescomparing the appliance data corresponding to a plurality of packetsreceived from a plurality of appliances to a plurality of performancedata corresponding to the respective plurality of appliances.
 7. Thesystem of claim 1, wherein the network computing device is configured togenerate a timestamp corresponding to receiving the packet to reduce asize of the packet transmitted through the network.
 8. The system ofclaim 1, wherein the network computing device is configured to generatea location tag corresponding to receipt of the packet.
 9. (canceled) 10.(canceled)
 11. A computer-implemented method for data transmission anddiagnostics for an appliance, the method comprising: periodicallytransmitting a plurality of packets from each of a plurality ofappliances to a remote server through a network, wherein each packetcomprises genealogical data encoded in a positional numeral system, thegenealogical data comprising a configuration identifier, a manufactureridentifier, a logistical identifier, a version identifier, orcombinations thereof, allowing for differentiation of one or morecomponents of the plurality of appliances based on one or more of theconfiguration identifier, the manufacturer identifier, the logisticalidentifier, or the version identifier, wherein differentiation of one ormore components of the plurality of appliances allows fordifferentiation of the plurality of appliances of similar model type;receiving, at the remote server, the plurality of packets from each ofthe plurality of appliances; decoding, at the remote server, thegenealogical data for each of the plurality the appliances, whereindecoding comprises translating the positional numeral system to anappliance configuration corresponding to each of the plurality ofappliances, comparing, at the remote server, appliance configurationscorresponding to each of the plurality of appliances, and determining,from comparing the appliance configurations, an operational parameteradjustment corresponding to one or more of the configuration identifier,the manufacturer identifier, the logistical identifier, or the versionidentifier associated with one or more appliance configurationscorresponding to one or more appliances of the plurality of appliances.12. The method of claim 11, the method comprising: transmitting theoperational parameter adjustment to the appliance via the remote serverand the network, wherein the operational parameter adjustment comprisesa control change, a software change, an operating limit, or anidentification of component replacement at the appliance to beimplemented by a technician.
 13. (canceled)
 14. The method of claim 11,the method comprising: comparing the plurality of applianceconfigurations corresponding to the plurality of appliances toperformance data; and determining the operational parameter adjustmentbased on comparing the appliance configuration to performance data. 15.(canceled)
 16. The method of claim 14, wherein determining theoperational parameter adjustment comprises comparing the appliance datacorresponding to the plurality of packets received from the plurality ofappliances to a plurality of performance data corresponding to therespective plurality of appliances.
 17. The method of claim 11, themethod comprising: generating, at the remote server, a timestampcorresponding to receiving each packet.
 18. The method of claim 11, themethod comprising: generating, at the remote server, a location tagcorresponding to receipt of the plurality of packets.
 19. The method ofclaim 11, wherein the positional numeral system is a hexadecimal numeralsystem.
 20. (canceled)
 21. The method of claim 11, wherein comparingappliance configurations comprises identifying a trend, a correlation, aregression, an interpolation, or an extrapolation associated with theappliance configurations of the plurality of appliances, and whereindetermining the operational parameter adjustment identifies a defectivecomponent associated with one or more appliance configurations.
 22. Themethod of claim 21, wherein the defective component comprises acomponent to be replaced or avoided in combination with one or moreother components of the appliance configuration associated with thedefective component.
 23. The method of claim 21, transmitting, from theremote server to the appliance corresponding to the defective component,a signal corresponding to the operational parameter adjustment, whereinthe operational parameter adjustment identifies a physical componentreplacement at the appliance to be implemented by a technician.
 24. Themethod of claim 17, the method comprising: comparing, at the remoteserver, a change in positional numeral value between the plurality ofpackets to respective timestamps corresponding to when each packet isreceived at the remote server to determine a time at which a componentchange or control change has occurred at the appliance.
 25. The systemof claim 1, wherein the network computing device is configured tocompare appliance configurations to identify a trend, a correlation, aregression, an interpolation, or an extrapolation associated with theappliance configurations of the plurality of appliances, and whereindetermining the operational parameter adjustment identifies a defectivecomponent associated with one or more appliance configurations.
 26. Thesystem of claim 25, wherein the defective component comprises acomponent to be replaced or avoided in combination with one or moreother components of the appliance configuration associated with thedefective component.